Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #2243: VarUsage failures reference a real tree #2244

Merged
merged 2 commits into from
May 2, 2022

Conversation

carterkozak
Copy link
Contributor

The var type tree is ambiguous and may not have a source
location, leading to confusing errors.

==COMMIT_MSG==
VarUsage failures reference a real tree
==COMMIT_MSG==

The `var` type tree is ambiguous and may not have a source
location, leading to confusing errors.
@changelog-app
Copy link

changelog-app bot commented May 2, 2022

Generate changelog in changelog/@unreleased

Type

  • Feature
  • Improvement
  • Fix
  • Break
  • Deprecation
  • Manual task
  • Migration

Description

VarUsage failures reference a real tree

Check the box to generate changelog(s)

  • Generate changelog entry

@bulldozer-bot bulldozer-bot bot merged commit 444a6e1 into develop May 2, 2022
@bulldozer-bot bulldozer-bot bot deleted the ckozak/VarUsage_real_type branch May 2, 2022 15:36
@svc-autorelease
Copy link
Collaborator

Released 4.124.0

bulldozer-bot bot pushed a commit to palantir/witchcraft-api that referenced this pull request May 2, 2022
###### _excavator_ is a bot for automating changes across repositories.

Changes produced by the roomba/latest-baseline-oss check.

# Release Notes
## 4.123.0
| Type | Description | Link |
| ---- | ----------- | ---- |
| Improvement | Fix safety evaluation requiring lhs of an assignment to be safe unnecessarily | palantir/gradle-baseline#2242 |


## 4.124.0
| Type | Description | Link |
| ---- | ----------- | ---- |
| Fix | VarUsage failures reference a real tree | palantir/gradle-baseline#2244 |



To enable or disable this check, please contact the maintainers of Excavator.
This was referenced May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants